Repository navigation
Run Dag processors without metadata database access - #74794
Open
ephraimbuddy wants to merge 2 commits into
Open
ephraimbuddy wants to merge 2 commits into
ephraimbuddy wants to merge 2 commits into
Conversation
boring-cyborg
Bot
added
area:API
ephraimbuddy
added this pull request to stack #74792
October 15, 2026 10:47
This was referenced Oct 15, 2026
ephraimbuddy
force-pushed
the
dag-processor-activation
branch
2 times, most recently
from
October 16, 2026 16:59
adf1913 to
8c7b7a2
Compare
ephraimbuddy
force-pushed
the
dag-processor-activation
branch
2 times, most recently
from
October 20, 2026 14:15
ea486c9 to
74ccd2d
Compare
ephraimbuddy
force-pushed
the
dag-processor-activation
branch
from
October 20, 2026 17:05
74ccd2d to
573c296
Compare
Standalone processors need to resolve bundle credentials and publish parsed metadata without inheriting database or signing credentials. API-managed Jobs also need lifecycle and requested-work recovery so transient outages do not lose callbacks or priority parses.
Delayed claim responses and repeated reparses must not consume newer work or lose the request that triggered a later import. API-mode processors also need consistent callback delivery semantics and bounded cleanup when recovering from interrupted work.
ephraimbuddy
force-pushed
the
dag-processor-activation
branch
from
October 20, 2026 17:24
573c296 to
6dbe8d3
Compare
ephraimbuddy
marked this pull request as ready for review
October 20, 2026 17:27
ephraimbuddy
requested review from
amoghrajesh,
ashb and
potiuk
as code owners
October 20, 2026 17:27
ephraimbuddy
requested review from
XD-DENG,
bugraoz93,
dheerajturaga,
henry3260 and
jedcunningham
as code owners
October 20, 2026 17:27
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable the complete opt-in processor API mode: registration, heartbeats, completion, callback and priority delivery, local health probes, and CLI configuration. The branch includes its prerequisite layers and can run the processor without metadata database credentials or database network access.
Layer 6 of the seven-part replacement for #74233, in GitHub native stack #74792. Depends on #74793. Base:
dag-processor-http-manager.GitHub's Files changed tab shows this layer. Compare this layer.
Merge order:
Replaces #74233 while preserving this activation layer as part 6. This PR builds on and reuses substantial parts of Kaxil Naik's implementation in #67878.
Closes #67878.
The full Task SDK suite passed (4,019 tests, 6 skipped). The complete processor candidate passed 72 focused runtime tests, including database-network isolation, signal handling, and API restart recovery. All 510 focused PostgreSQL tests passed on the final split branch, including both database-network isolation cases (509 in the suite; one CLI subprocess passed an unchanged isolated retry after exceeding its 90-second deadline under concurrent test load). Regular and manual static checks passed.
Core, Task SDK, common.compat, and FAB documentation builds passed. Broader local suites are not fully green: baseline file-descriptor and plugin-discovery failures were reproduced on unchanged code; other existing tests timed out under emulation, and two provider groups stalled inside Polars. Focused results above are recorded separately from those broader limitations.
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-6) following the guidelines